Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fea050ed209d82f70eb5ff38e77898e164d6dccdf3f8c93f4446d2bc8437f4b4

Tx prefix hash: 15e22948cc54c4e5d0ae97d48c20dc710e563a38b4d2c0b79dd1999d51ceecf5
Tx public key: e5052dcffe361fcf28c828bfa506b41dfe7ef0c205ef96664be870a54f3565c5
Timestamp: 1702704115 Timestamp [UCT]: 2023-12-16 05:21:55 Age [y:d:h:m:s]: 01:036:02:54:16
Block: 914166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287120 RingCT/type: yes/0
Extra: 01e5052dcffe361fcf28c828bfa506b41dfe7ef0c205ef96664be870a54f3565c502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7be1ba2cbc34f49e8c3076ad6bd14d2dc9c046b99c168e0be9e3af331782766 0.600000000000 1371452 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 914176, "vin": [ { "gen": { "height": 914166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7be1ba2cbc34f49e8c3076ad6bd14d2dc9c046b99c168e0be9e3af331782766" } } ], "extra": [ 1, 229, 5, 45, 207, 254, 54, 31, 207, 40, 200, 40, 191, 165, 6, 180, 29, 254, 126, 240, 194, 5, 239, 150, 102, 75, 232, 112, 165, 79, 53, 101, 197, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8