Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce9834a64514ebea6af78937c3dcf54b9e08e0ea27435641048852139983689c

Tx prefix hash: 9ea19d051f22a214957472aa1e1f7e1a9e1e58be3685584b0d5c23e85d438467
Tx public key: b5de8d3ea26f084458c7d9a02594e7063c242375e97d7e4108dfc16224bf8945
Timestamp: 1704483116 Timestamp [UCT]: 2024-01-05 19:31:56 Age [y:d:h:m:s]: 01:310:09:55:08
Block: 928904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480674 RingCT/type: yes/0
Extra: 01b5de8d3ea26f084458c7d9a02594e7063c242375e97d7e4108dfc16224bf89450211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9ef96192b85c465c98539a518f9aa1a70b289253578c1a045ae880dd2847663 0.600000000000 1386770 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": 928914, "vin": [ { "gen": { "height": 928904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9ef96192b85c465c98539a518f9aa1a70b289253578c1a045ae880dd2847663" } } ], "extra": [ 1, 181, 222, 141, 62, 162, 111, 8, 68, 88, 199, 217, 160, 37, 148, 231, 6, 60, 36, 35, 117, 233, 125, 126, 65, 8, 223, 193, 98, 36, 191, 137, 69, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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