Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 920ff0159171aa7dd0cabfcd88ecc91a1051e0653a292ede29dd6e2f77ab91a8

Tx prefix hash: e287d5a329711eae6d770c29223de8be1c8e8057c9bceecfd4c201f1b1b3ee98
Tx public key: e909dc80c5a90015f8b6b10a475f5ff417d3f8aa336fdc6464a3b028ba442daf
Timestamp: 1721252952 Timestamp [UCT]: 2024-07-17 21:49:12 Age [y:d:h:m:s]: 01:113:04:19:24
Block: 1067956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339381 RingCT/type: yes/0
Extra: 01e909dc80c5a90015f8b6b10a475f5ff417d3f8aa336fdc6464a3b028ba442daf02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da3c63672b57a9a8e64176abf4008536e837edb6d7f0b5d88b8df87ae826b279 0.600000000000 1538913 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": 1067966, "vin": [ { "gen": { "height": 1067956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da3c63672b57a9a8e64176abf4008536e837edb6d7f0b5d88b8df87ae826b279" } } ], "extra": [ 1, 233, 9, 220, 128, 197, 169, 0, 21, 248, 182, 177, 10, 71, 95, 95, 244, 23, 211, 248, 170, 51, 111, 220, 100, 100, 163, 176, 40, 186, 68, 45, 175, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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