Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0963de4317ee9a90db051294cdb6e1e816b38de73143c7074bf38d5182cda994

Tx prefix hash: 364d375ac131aa77e6f96cc9be03aa758a9dfa93b4af53d47fc009c00cab44e4
Tx public key: b28c23dce6659e9c96bb1d0f1f32fa108cc4ad76008609bfa61049e3c2b79929
Timestamp: 1704286972 Timestamp [UCT]: 2024-01-03 13:02:52 Age [y:d:h:m:s]: 01:354:18:33:47
Block: 927290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512424 RingCT/type: yes/0
Extra: 01b28c23dce6659e9c96bb1d0f1f32fa108cc4ad76008609bfa61049e3c2b79929021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e3fc7845c484775d7d975b75f2ae0d8310b5f2b44a296c1a2557bc7d501b46f 0.600000000000 1385122 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": 927300, "vin": [ { "gen": { "height": 927290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e3fc7845c484775d7d975b75f2ae0d8310b5f2b44a296c1a2557bc7d501b46f" } } ], "extra": [ 1, 178, 140, 35, 220, 230, 101, 158, 156, 150, 187, 29, 15, 31, 50, 250, 16, 140, 196, 173, 118, 0, 134, 9, 191, 166, 16, 73, 227, 194, 183, 153, 41, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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