Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d973170a4d99320820c1309fd74afbe97bba826c9b7484de2cdea78d93438c11

Tx prefix hash: ee2253ba50632282842b2749a9e89d12755ab13211c61c6d5bcd79898bc06152
Tx public key: d9df0d9aa3473077f03b66860ab2eb82f8ad66e8bf238fb567219b5d3cac46f3
Timestamp: 1731976276 Timestamp [UCT]: 2024-11-19 00:31:16 Age [y:d:h:m:s]: 00:150:05:32:56
Block: 1156757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107195 RingCT/type: yes/0
Extra: 01d9df0d9aa3473077f03b66860ab2eb82f8ad66e8bf238fb567219b5d3cac46f30211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a76c9dc9ef900eac81f4472e9849ae981815226e9e678ce7a5eefdb8d8ab1c0 0.600000000000 1642380 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": 1156767, "vin": [ { "gen": { "height": 1156757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a76c9dc9ef900eac81f4472e9849ae981815226e9e678ce7a5eefdb8d8ab1c0" } } ], "extra": [ 1, 217, 223, 13, 154, 163, 71, 48, 119, 240, 59, 102, 134, 10, 178, 235, 130, 248, 173, 102, 232, 191, 35, 143, 181, 103, 33, 155, 93, 60, 172, 70, 243, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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