Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547d214a3e62dc2eb40372f24fb6784db86b38b38edcd0f6aefb0ec33e47f56d

Tx prefix hash: c4617637a60fc8ea0b99e1be3bfe3cba8c4ab8313140611ee69e202687c5131d
Tx public key: 0060897a0bcdf2226d1945d6ac0b6bbb572cf0c4abc20ae18ceddede0319c86c
Timestamp: 1732097597 Timestamp [UCT]: 2024-11-20 10:13:17 Age [y:d:h:m:s]: 00:003:19:07:44
Block: 1157744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2728 RingCT/type: yes/0
Extra: 010060897a0bcdf2226d1945d6ac0b6bbb572cf0c4abc20ae18ceddede0319c86c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 720a64ed7a6d7a1fe730d5c6277529ef9851f3bf4f0844d0c7e5a1de4e4f91aa 0.600000000000 1643367 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": 1157754, "vin": [ { "gen": { "height": 1157744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "720a64ed7a6d7a1fe730d5c6277529ef9851f3bf4f0844d0c7e5a1de4e4f91aa" } } ], "extra": [ 1, 0, 96, 137, 122, 11, 205, 242, 34, 109, 25, 69, 214, 172, 11, 107, 187, 87, 44, 240, 196, 171, 194, 10, 225, 140, 237, 222, 222, 3, 25, 200, 108, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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