Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69bbf298b514cc6d8200c71f9bae3e2a998501604cc0b22399e5b6d9bae71bb0

Tx prefix hash: d717f5d555f74c3202db73289dcce9eee1ec216afc4d9b663c8cdc58a9d988a4
Tx public key: 40757cd0469f284fab66025ef68eaf4b53dc0eb00731a14174cdf856dc1c05e7
Timestamp: 1703651053 Timestamp [UCT]: 2023-12-27 04:24:13 Age [y:d:h:m:s]: 01:173:12:14:02
Block: 922013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385056 RingCT/type: yes/0
Extra: 0140757cd0469f284fab66025ef68eaf4b53dc0eb00731a14174cdf856dc1c05e7021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63e4104f3a05308d98a832ddb1e689547703e58a5e2e47bd6a8260c13d7f6148 0.600000000000 1379707 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": 922023, "vin": [ { "gen": { "height": 922013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63e4104f3a05308d98a832ddb1e689547703e58a5e2e47bd6a8260c13d7f6148" } } ], "extra": [ 1, 64, 117, 124, 208, 70, 159, 40, 79, 171, 102, 2, 94, 246, 142, 175, 75, 83, 220, 14, 176, 7, 49, 161, 65, 116, 205, 248, 86, 220, 28, 5, 231, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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