Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 892c594da779439fdb0fd901fcd49a92cea9110c32014aeeac7a6caf6d3cb39f

Tx prefix hash: 81a8c313e5896afb3aaa15ee81ad437d0993c8a2ee5a99416ffbfcff71101c8d
Tx public key: 72e590c7eae90a32b1077338ff3cca21f00e89da51fcc5b6f66628e9a24f6ee6
Timestamp: 1632977281 Timestamp [UCT]: 2021-09-30 04:48:01 Age [y:d:h:m:s]: 03:051:07:16:07
Block: 343519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 813582 RingCT/type: yes/0
Extra: 0172e590c7eae90a32b1077338ff3cca21f00e89da51fcc5b6f66628e9a24f6ee6021100000019f29d7abf000000000000000000

1 output(s) for total of 44.645673723000 dcy

stealth address amount amount idx
00: 29d4c2f21d2a4f5376ea1e060aa9b371f97d65e217d059a6b5a76a5f58ad1b4b 44.645673723000 705118 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": 343529, "vin": [ { "gen": { "height": 343519 } } ], "vout": [ { "amount": 44645673723, "target": { "key": "29d4c2f21d2a4f5376ea1e060aa9b371f97d65e217d059a6b5a76a5f58ad1b4b" } } ], "extra": [ 1, 114, 229, 144, 199, 234, 233, 10, 50, 177, 7, 115, 56, 255, 60, 202, 33, 240, 14, 137, 218, 81, 252, 197, 182, 246, 102, 40, 233, 162, 79, 110, 230, 2, 17, 0, 0, 0, 25, 242, 157, 122, 191, 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