Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec2107cf64c0f5e8b2d3461b8e57cd15a47ca3a669d7c2fcb240f82c9d836577

Tx prefix hash: c28288e9ec1c124c5daba48f534160d0acaaa8118fb0438900c6191de6fe5709
Tx public key: 72909186a6028f91093a5ee083cdbe9072b76fff7a6f376eaa7cb3b806245487
Timestamp: 1715763128 Timestamp [UCT]: 2024-05-15 08:52:08 Age [y:d:h:m:s]: 00:240:09:20:54
Block: 1022437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172044 RingCT/type: yes/0
Extra: 0172909186a6028f91093a5ee083cdbe9072b76fff7a6f376eaa7cb3b806245487021100000008e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71bb2dbaf5a36a63131bd37c5d54a48b0cf2f3a47720d595c26f80a357391352 0.600000000000 1487038 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": 1022447, "vin": [ { "gen": { "height": 1022437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71bb2dbaf5a36a63131bd37c5d54a48b0cf2f3a47720d595c26f80a357391352" } } ], "extra": [ 1, 114, 144, 145, 134, 166, 2, 143, 145, 9, 58, 94, 224, 131, 205, 190, 144, 114, 183, 111, 255, 122, 111, 55, 110, 170, 124, 179, 184, 6, 36, 84, 135, 2, 17, 0, 0, 0, 8, 224, 133, 50, 182, 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