Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea27d7eaa4a29ba29173270866684a7d1f679199789f884ff47f838592e2a7a

Tx prefix hash: ccbf5b5be769040bad95d4f9f5471b0ee4f2dcc5bba9893034d2858f0e307c60
Tx public key: 5f10ef51e1c1135b10d171d8f1da762a1222cb6dd35718d781058ef4f8a7e53d
Timestamp: 1649817468 Timestamp [UCT]: 2022-04-13 02:37:48 Age [y:d:h:m:s]: 02:336:23:25:01
Block: 479035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 760498 RingCT/type: yes/0
Extra: 015f10ef51e1c1135b10d171d8f1da762a1222cb6dd35718d781058ef4f8a7e53d021100000001d3fcec30000000000000000000

1 output(s) for total of 15.876633675000 dcy

stealth address amount amount idx
00: 0f1091eaae6517269bb810096d17e59c1bc6ee55dca248c6433ddde72bfeece0 15.876633675000 899858 of 0

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": 479045, "vin": [ { "gen": { "height": 479035 } } ], "vout": [ { "amount": 15876633675, "target": { "key": "0f1091eaae6517269bb810096d17e59c1bc6ee55dca248c6433ddde72bfeece0" } } ], "extra": [ 1, 95, 16, 239, 81, 225, 193, 19, 91, 16, 209, 113, 216, 241, 218, 118, 42, 18, 34, 203, 109, 211, 87, 24, 215, 129, 5, 142, 244, 248, 167, 229, 61, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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