Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21034dd0ef35f88ae68dde04d7a9c66f2de8339b1c9372588d6edee665edcde0

Tx prefix hash: 758d4d671939f44b60b66cde6621490d23a3b693d54a5e100fe65cef4f8cbba7
Tx public key: 837eb84678499557be3f3c83f9e78ee35f6b00f8316ccbc96c50cff3812fb4a7
Timestamp: 1705972622 Timestamp [UCT]: 2024-01-23 01:17:02 Age [y:d:h:m:s]: 01:286:05:45:57
Block: 941228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463397 RingCT/type: yes/0
Extra: 01837eb84678499557be3f3c83f9e78ee35f6b00f8316ccbc96c50cff3812fb4a702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f67db8f8f08b9986e3d362f7b6dfa1c3fd79c7092ac261d97400b07e33f2d15 0.600000000000 1399374 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": 941238, "vin": [ { "gen": { "height": 941228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f67db8f8f08b9986e3d362f7b6dfa1c3fd79c7092ac261d97400b07e33f2d15" } } ], "extra": [ 1, 131, 126, 184, 70, 120, 73, 149, 87, 190, 63, 60, 131, 249, 231, 142, 227, 95, 107, 0, 248, 49, 108, 203, 201, 108, 80, 207, 243, 129, 47, 180, 167, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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