Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 821bf3b75d34869ab0ca4b903318c2dcfbf07023f51833f240a4106dc6b8daa1

Tx prefix hash: 18f1b1b133c99aa954a190247067f4e78941315d8a35cca0d800639d740b5b63
Tx public key: 74dbd4bf71b7e7b33c46d5d8af83f8f718923fc0f7ef09e9f93eb15e5e34838d
Timestamp: 1697353021 Timestamp [UCT]: 2023-10-15 06:57:01 Age [y:d:h:m:s]: 01:097:04:38:31
Block: 869999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330683 RingCT/type: yes/0
Extra: 0174dbd4bf71b7e7b33c46d5d8af83f8f718923fc0f7ef09e9f93eb15e5e34838d02110000000433af99f4000000000000000000

1 output(s) for total of 0.804140965000 dcy

stealth address amount amount idx
00: 7a7867fde65051e5614d74f78b7e59b286c9a9d7a694267c8d5a739d6f299db0 0.804140965000 1324866 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": 870009, "vin": [ { "gen": { "height": 869999 } } ], "vout": [ { "amount": 804140965, "target": { "key": "7a7867fde65051e5614d74f78b7e59b286c9a9d7a694267c8d5a739d6f299db0" } } ], "extra": [ 1, 116, 219, 212, 191, 113, 183, 231, 179, 60, 70, 213, 216, 175, 131, 248, 247, 24, 146, 63, 192, 247, 239, 9, 233, 249, 62, 177, 94, 94, 52, 131, 141, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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