Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccc93fd2dda510b1829d4953ba570a68884d3ed3679ea93a9f9a2f64f6076b32

Tx prefix hash: bb492f9cd5ff898665fd7c3bc5836cc3035cd6808ff280f083dab931fbe273ae
Tx public key: 32753e87492c53581f567ea77d4398a714defa4c66c90f9879785b90e0819f5d
Timestamp: 1577058417 Timestamp [UCT]: 2019-12-22 23:46:57 Age [y:d:h:m:s]: 05:007:22:47:28
Block: 29774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155534 RingCT/type: yes/0
Extra: 0132753e87492c53581f567ea77d4398a714defa4c66c90f9879785b90e0819f5d0211000000308a2ee0d9000000000000000000

1 output(s) for total of 489.043218346000 dcy

stealth address amount amount idx
00: 09421a23f684f6e223581120050c4b96ffa94add590b92474caf75fb3881bc3a 489.043218346000 49066 of 0

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": 29784, "vin": [ { "gen": { "height": 29774 } } ], "vout": [ { "amount": 489043218346, "target": { "key": "09421a23f684f6e223581120050c4b96ffa94add590b92474caf75fb3881bc3a" } } ], "extra": [ 1, 50, 117, 62, 135, 73, 44, 83, 88, 31, 86, 126, 167, 125, 67, 152, 167, 20, 222, 250, 76, 102, 201, 15, 152, 121, 120, 91, 144, 224, 129, 159, 93, 2, 17, 0, 0, 0, 48, 138, 46, 224, 217, 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