Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d9009b801b72e43febca1fc141c5ed8dddb46a3525db388ecaeba04962a8fc6

Tx prefix hash: 1375b1722fa81e93cd03f82a8232da18ac8b739b18e40f41a3c1897fe4600755
Tx public key: 04aca9293395ad6318f91e5544fa4d9196a0df6a342b72fc9c1559a3dfcfdf8c
Timestamp: 1696969975 Timestamp [UCT]: 2023-10-10 20:32:55 Age [y:d:h:m:s]: 02:028:03:09:48
Block: 866836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539708 RingCT/type: yes/0
Extra: 0104aca9293395ad6318f91e5544fa4d9196a0df6a342b72fc9c1559a3dfcfdf8c021100000002faf35c9c000000000000000000

1 output(s) for total of 0.823782427000 dcy

stealth address amount amount idx
00: 363e50bda63754468d76f282d936a3ba820bf4196fe4a124bfb73efc9e8efed9 0.823782427000 1321474 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": 866846, "vin": [ { "gen": { "height": 866836 } } ], "vout": [ { "amount": 823782427, "target": { "key": "363e50bda63754468d76f282d936a3ba820bf4196fe4a124bfb73efc9e8efed9" } } ], "extra": [ 1, 4, 172, 169, 41, 51, 149, 173, 99, 24, 249, 30, 85, 68, 250, 77, 145, 150, 160, 223, 106, 52, 43, 114, 252, 156, 21, 89, 163, 223, 207, 223, 140, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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