Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f9ce3514c0ce86dd9f88b8474d395230e199fca323aef8d95ffb1919d72db64

Tx prefix hash: 0ceb0bd80c773c0d03f464745f62a0ffb6c32ce9e2cb75de9db763dbdd40c4e3
Tx public key: baa3ecb30f4f1f608bbe3ac6d11dca7649cddd4abafb9e94dc231696556fe9ed
Timestamp: 1727780686 Timestamp [UCT]: 2024-10-01 11:04:46 Age [y:d:h:m:s]: 00:181:22:19:27
Block: 1122065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129812 RingCT/type: yes/0
Extra: 01baa3ecb30f4f1f608bbe3ac6d11dca7649cddd4abafb9e94dc231696556fe9ed021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 621256aa1648b9d2ae03151d6fb1ac794dc4a93646b68c512d9e668fc1e3c8c2 0.600000000000 1604436 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": 1122075, "vin": [ { "gen": { "height": 1122065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "621256aa1648b9d2ae03151d6fb1ac794dc4a93646b68c512d9e668fc1e3c8c2" } } ], "extra": [ 1, 186, 163, 236, 179, 15, 79, 31, 96, 139, 190, 58, 198, 209, 29, 202, 118, 73, 205, 221, 74, 186, 251, 158, 148, 220, 35, 22, 150, 85, 111, 233, 237, 2, 17, 0, 0, 0, 5, 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