Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f487117f1db91fda5c37e84f8037f40f8e75ca3b4e30f32ae493cd98279daf53

Tx prefix hash: ebe881c7800dfa41c570d3bda75ae72b5a04740d2fc0269955c5d766baeb52d0
Tx public key: edc3b31721e87b446474b354e80b7d6ef2e23a33d096e0d4e0b3614b743af23e
Timestamp: 1709998649 Timestamp [UCT]: 2024-03-09 15:37:29 Age [y:d:h:m:s]: 01:080:16:15:25
Block: 974641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318705 RingCT/type: yes/0
Extra: 01edc3b31721e87b446474b354e80b7d6ef2e23a33d096e0d4e0b3614b743af23e0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f7cbb41be8054028e1aa1b51daaf8f1a88a4889b7baa508eda5a842c6295c64 0.600000000000 1434600 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": 974651, "vin": [ { "gen": { "height": 974641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f7cbb41be8054028e1aa1b51daaf8f1a88a4889b7baa508eda5a842c6295c64" } } ], "extra": [ 1, 237, 195, 179, 23, 33, 232, 123, 68, 100, 116, 179, 84, 232, 11, 125, 110, 242, 226, 58, 51, 208, 150, 224, 212, 224, 179, 97, 75, 116, 58, 242, 62, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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