Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daf3644e7524a42ae8549f7f11e4a85cc0c7cf6c7ee299c4fd811c46d9810928

Tx prefix hash: 657cb2e37b2145c00bcb0fb9339177599efe0f54d33730174b3a463c12135516
Tx public key: 87349037918d2bf2935392f6999c7f3c48c40f014c6dfea8502bc355cde26d03
Timestamp: 1760918729 Timestamp [UCT]: 2025-10-20 00:05:29 Age [y:d:h:m:s]: 00:063:00:25:41
Block: 1393691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45104 RingCT/type: yes/0
Extra: 0187349037918d2bf2935392f6999c7f3c48c40f014c6dfea8502bc355cde26d0302110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d68fc9929205083bb0f8c6e6e6d77f5e7a00a197a7f48c71e3d611c759ca7cfc 0.600000000000 1881956 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": 1393701, "vin": [ { "gen": { "height": 1393691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d68fc9929205083bb0f8c6e6e6d77f5e7a00a197a7f48c71e3d611c759ca7cfc" } } ], "extra": [ 1, 135, 52, 144, 55, 145, 141, 43, 242, 147, 83, 146, 246, 153, 156, 127, 60, 72, 196, 15, 1, 76, 109, 254, 168, 80, 43, 195, 85, 205, 226, 109, 3, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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