Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f2e14b927ad07a8ea55b31c106f041a282961605833fbe27864723ca38529b

Tx prefix hash: 852bbf94274d7dc3345691608e68f871f64d44bd9ea7e5e919cf828128850f69
Tx public key: 632ae4d30a17d48e2e78ca4b6b267e85991ef8d7925f2ff7d711a3cc8b2bbe37
Timestamp: 1731989655 Timestamp [UCT]: 2024-11-19 04:14:15 Age [y:d:h:m:s]: 01:001:15:08:15
Block: 1156863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259578 RingCT/type: yes/0
Extra: 01632ae4d30a17d48e2e78ca4b6b267e85991ef8d7925f2ff7d711a3cc8b2bbe37021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07d1a032a7d91d353763aa5739621b408ae24178d30c799a143ea463e37b2ecc 0.600000000000 1642486 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": 1156873, "vin": [ { "gen": { "height": 1156863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07d1a032a7d91d353763aa5739621b408ae24178d30c799a143ea463e37b2ecc" } } ], "extra": [ 1, 99, 42, 228, 211, 10, 23, 212, 142, 46, 120, 202, 75, 107, 38, 126, 133, 153, 30, 248, 215, 146, 95, 47, 247, 215, 17, 163, 204, 139, 43, 190, 55, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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