Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f453d68583276a19ff9637c84c54deb5f0a7982b10cfa66cc4f17061621b91ec

Tx prefix hash: 3b07da3b31694151fa9d14e92616e0ddc43c36fbd22eca75f3599beec5ca7ac4
Tx public key: 3a9c68fc3e2fe9f552d6bd8f7e393e499018f56619c39badf54e4fd2ac187faa
Timestamp: 1727191013 Timestamp [UCT]: 2024-09-24 15:16:53 Age [y:d:h:m:s]: 00:258:06:35:15
Block: 1117180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184444 RingCT/type: yes/0
Extra: 013a9c68fc3e2fe9f552d6bd8f7e393e499018f56619c39badf54e4fd2ac187faa021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97c161be3ea3aaee02f3bbab4ad72b42e73ccda82db0b622a97856c8bbe0f9f7 0.600000000000 1597923 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": 1117190, "vin": [ { "gen": { "height": 1117180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97c161be3ea3aaee02f3bbab4ad72b42e73ccda82db0b622a97856c8bbe0f9f7" } } ], "extra": [ 1, 58, 156, 104, 252, 62, 47, 233, 245, 82, 214, 189, 143, 126, 57, 62, 73, 144, 24, 245, 102, 25, 195, 155, 173, 245, 78, 79, 210, 172, 24, 127, 170, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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