Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e626826e11a0f49a19394e78f7cb51fa49ee89162af7697c5ceb4aff13ccf21

Tx prefix hash: 4d910d97c3de111f7047531c3c08f155a8be4a83b48df668ca4fa91597a4f67a
Tx public key: d400e7b231973229a25e4b7769c340a9eba6e6e51074afde2084bf8fcb524ed8
Timestamp: 1713245039 Timestamp [UCT]: 2024-04-16 05:23:59 Age [y:d:h:m:s]: 01:204:08:36:08
Block: 1001537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404702 RingCT/type: yes/0
Extra: 01d400e7b231973229a25e4b7769c340a9eba6e6e51074afde2084bf8fcb524ed802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a426819d7ae41bc46665c7d7a97aa101f1ffa00cf2086ce3d445fa7ef1e68356 0.600000000000 1462043 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": 1001547, "vin": [ { "gen": { "height": 1001537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a426819d7ae41bc46665c7d7a97aa101f1ffa00cf2086ce3d445fa7ef1e68356" } } ], "extra": [ 1, 212, 0, 231, 178, 49, 151, 50, 41, 162, 94, 75, 119, 105, 195, 64, 169, 235, 166, 230, 229, 16, 116, 175, 222, 32, 132, 191, 143, 203, 82, 78, 216, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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