Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a77f59343854e39cb916cb96e9a193fd48e82e769fa8e4c8c2072b913734676

Tx prefix hash: cd0d7b7e44d8d1a44fea346811f76a7ad36cd4dad23fc48a0373e01ee72f54cd
Tx public key: 6b305f233bd1fcf39329fd78df34d413dde0d6959dac0738b5e1ce12ea47e8bf
Timestamp: 1705127251 Timestamp [UCT]: 2024-01-13 06:27:31 Age [y:d:h:m:s]: 01:151:07:25:10
Block: 934229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369256 RingCT/type: yes/0
Extra: 016b305f233bd1fcf39329fd78df34d413dde0d6959dac0738b5e1ce12ea47e8bf021100000001ac328d11000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 821153e46d6189bb8fe94449c56f4f6ded847cc9287cc75f2ac30cf379739617 0.600000000000 1392219 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": 934239, "vin": [ { "gen": { "height": 934229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "821153e46d6189bb8fe94449c56f4f6ded847cc9287cc75f2ac30cf379739617" } } ], "extra": [ 1, 107, 48, 95, 35, 59, 209, 252, 243, 147, 41, 253, 120, 223, 52, 212, 19, 221, 224, 214, 149, 157, 172, 7, 56, 181, 225, 206, 18, 234, 71, 232, 191, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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