Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 713973555568572af6c97f6cb737bd490d44159c9733fae74729088409e28fdc

Tx prefix hash: a113b612396e3f082c70b4cfd4727c2e6c687b556c20daa9fce662964c804ada
Tx public key: 603306716d4b98e80cb116174b4b8cc918b9e3c897acd94e47fcfca0e20f2e76
Timestamp: 1645582735 Timestamp [UCT]: 2022-02-23 02:18:55 Age [y:d:h:m:s]: 03:088:07:44:28
Block: 444461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 843218 RingCT/type: yes/0
Extra: 01603306716d4b98e80cb116174b4b8cc918b9e3c897acd94e47fcfca0e20f2e76021100000006bf7ee4e7000000000000000000

1 output(s) for total of 20.668858370000 dcy

stealth address amount amount idx
00: 04b9aeb7128e6b58197fde70200563ce4162b846d3ba49b0a1053db34e9412b2 20.668858370000 857756 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": 444471, "vin": [ { "gen": { "height": 444461 } } ], "vout": [ { "amount": 20668858370, "target": { "key": "04b9aeb7128e6b58197fde70200563ce4162b846d3ba49b0a1053db34e9412b2" } } ], "extra": [ 1, 96, 51, 6, 113, 109, 75, 152, 232, 12, 177, 22, 23, 75, 75, 140, 201, 24, 185, 227, 200, 151, 172, 217, 78, 71, 252, 252, 160, 226, 15, 46, 118, 2, 17, 0, 0, 0, 6, 191, 126, 228, 231, 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