Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b02ee1c4e1e1862514775745d07817af1323b6574d5365b21710022a1c591454

Tx prefix hash: 57d70c69dfcfc71c929f41adeae645d6049e3750e0d64ad8d59cc2506f9c8271
Tx public key: eb56f23d8bd21101a5e9601c333dafbcb9a36741c5c6afa660897916bbf8d088
Timestamp: 1744371955 Timestamp [UCT]: 2025-04-11 11:45:55 Age [y:d:h:m:s]: 00:254:18:00:19
Block: 1259121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179826 RingCT/type: yes/0
Extra: 01eb56f23d8bd21101a5e9601c333dafbcb9a36741c5c6afa660897916bbf8d088021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 706f0d905b89df425f3e6e760fb7015b3050f5bef45ac61927d4c1ef3a6b60d2 0.600000000000 1746260 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": 1259131, "vin": [ { "gen": { "height": 1259121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "706f0d905b89df425f3e6e760fb7015b3050f5bef45ac61927d4c1ef3a6b60d2" } } ], "extra": [ 1, 235, 86, 242, 61, 139, 210, 17, 1, 165, 233, 96, 28, 51, 61, 175, 188, 185, 163, 103, 65, 197, 198, 175, 166, 96, 137, 121, 22, 187, 248, 208, 136, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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