Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a411f811d638eb050d471bc85bfd4a2a6f6e71f83f3bdb5e00a50a165982b7c3

Tx prefix hash: a350dbfb6eaecf7b590754a10fed5a3f941e64b1e918e7e671515a5e6481fa30
Tx public key: 742f2780deb3eaf20b53948dae94196c6b4104d5acd958524af1836bc537ebf6
Timestamp: 1722931274 Timestamp [UCT]: 2024-08-06 08:01:14 Age [y:d:h:m:s]: 00:200:14:27:57
Block: 1081853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143222 RingCT/type: yes/0
Extra: 01742f2780deb3eaf20b53948dae94196c6b4104d5acd958524af1836bc537ebf6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbc57f8a874881431f28bee6fa54513dc1f4907e20b4d8f8a745ad9aeee11883 0.600000000000 1555676 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": 1081863, "vin": [ { "gen": { "height": 1081853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbc57f8a874881431f28bee6fa54513dc1f4907e20b4d8f8a745ad9aeee11883" } } ], "extra": [ 1, 116, 47, 39, 128, 222, 179, 234, 242, 11, 83, 148, 141, 174, 148, 25, 108, 107, 65, 4, 213, 172, 217, 88, 82, 74, 241, 131, 107, 197, 55, 235, 246, 2, 17, 0, 0, 0, 1, 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