Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3603fb14004d2dbdb2bf3f625c3cb2b98161fbffd864b49d6a57ed1fd22b185

Tx prefix hash: d649752e659a2c1a15be29709ad0edfad8a425f5b4d15a24d982de33d9f0d246
Tx public key: 931ca45de0db7b7505b42b973cfc68ff776dd587274e04e9a03ddd6bb16b3448
Timestamp: 1732076127 Timestamp [UCT]: 2024-11-20 04:15:27 Age [y:d:h:m:s]: 00:003:21:21:34
Block: 1157569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2797 RingCT/type: yes/0
Extra: 01931ca45de0db7b7505b42b973cfc68ff776dd587274e04e9a03ddd6bb16b34480211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4c8ef58213fd634b57ef528907de883accd7c66b8c8f106e1dfdbdbe0ce749b 0.600000000000 1643192 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": 1157579, "vin": [ { "gen": { "height": 1157569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4c8ef58213fd634b57ef528907de883accd7c66b8c8f106e1dfdbdbe0ce749b" } } ], "extra": [ 1, 147, 28, 164, 93, 224, 219, 123, 117, 5, 180, 43, 151, 60, 252, 104, 255, 119, 109, 213, 135, 39, 78, 4, 233, 160, 61, 221, 107, 177, 107, 52, 72, 2, 17, 0, 0, 0, 3, 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