Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: badfe55233ebecb502e7f287fe67d2ec5981bc3a271ae4f704d1a04f713c225e

Tx prefix hash: 0a84c63fd236663276f3e389fd75ace5c26385b72c70da8706449ba87c1c1b99
Tx public key: 902604e4ef586be33e5e373f9c2ff0b81fea0abb66778e9dfd454893d4417634
Timestamp: 1733052160 Timestamp [UCT]: 2024-12-01 11:22:40 Age [y:d:h:m:s]: 00:122:16:13:16
Block: 1165671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87461 RingCT/type: yes/0
Extra: 01902604e4ef586be33e5e373f9c2ff0b81fea0abb66778e9dfd454893d4417634021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48da45fb2f4b5f70426e9d073c40fa20b9dbd1dd6eb029bbe7eaf3d5f39fea69 0.600000000000 1651346 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": 1165681, "vin": [ { "gen": { "height": 1165671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48da45fb2f4b5f70426e9d073c40fa20b9dbd1dd6eb029bbe7eaf3d5f39fea69" } } ], "extra": [ 1, 144, 38, 4, 228, 239, 88, 107, 227, 62, 94, 55, 63, 156, 47, 240, 184, 31, 234, 10, 187, 102, 119, 142, 157, 253, 69, 72, 147, 212, 65, 118, 52, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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