Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d32ea8b618b1e08e4940efc1fb84b3e5fcfec9eb361ba0c4e370344292132e3

Tx prefix hash: bf9427931601ad8cc6d4b60a833ebfb341a8f793a79ddc49852beab4983621ba
Tx public key: 8a0503b26697fe6287a80b228c35e6d606e3aa420d4af95ea58ea732273fde6e
Timestamp: 1740763151 Timestamp [UCT]: 2025-02-28 17:19:11 Age [y:d:h:m:s]: 00:301:22:55:11
Block: 1229227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213618 RingCT/type: yes/0
Extra: 018a0503b26697fe6287a80b228c35e6d606e3aa420d4af95ea58ea732273fde6e0211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05bc966a549a23cc7b23c61f5be5daf324f4eb271dade9323aaf7bfd38f5ece3 0.600000000000 1716112 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": 1229237, "vin": [ { "gen": { "height": 1229227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05bc966a549a23cc7b23c61f5be5daf324f4eb271dade9323aaf7bfd38f5ece3" } } ], "extra": [ 1, 138, 5, 3, 178, 102, 151, 254, 98, 135, 168, 11, 34, 140, 53, 230, 214, 6, 227, 170, 66, 13, 74, 249, 94, 165, 142, 167, 50, 39, 63, 222, 110, 2, 17, 0, 0, 0, 9, 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