Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cc4f702528c0bff073c8cd890824bbf20e2baf4d68d6c4fb26ce3a58450ffd3

Tx prefix hash: b075544936f0702e198896ec04771146d18f670303ef582f0802425888430788
Tx public key: 22c59d05fce259dd5e9c92c1547715e677d22ac4e528e905a6f8cb82b6b871cb
Timestamp: 1695563978 Timestamp [UCT]: 2023-09-24 13:59:38 Age [y:d:h:m:s]: 01:193:17:48:58
Block: 855167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399533 RingCT/type: yes/0
Extra: 0122c59d05fce259dd5e9c92c1547715e677d22ac4e528e905a6f8cb82b6b871cb021100000002faf35c9c000000000000000000

1 output(s) for total of 0.900485619000 dcy

stealth address amount amount idx
00: 8e79f804ac129b1d9612ee69a8e79fe8f275b9bcdbffdc9db4a6923287e2d4c5 0.900485619000 1309171 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": 855177, "vin": [ { "gen": { "height": 855167 } } ], "vout": [ { "amount": 900485619, "target": { "key": "8e79f804ac129b1d9612ee69a8e79fe8f275b9bcdbffdc9db4a6923287e2d4c5" } } ], "extra": [ 1, 34, 197, 157, 5, 252, 226, 89, 221, 94, 156, 146, 193, 84, 119, 21, 230, 119, 210, 42, 196, 229, 40, 233, 5, 166, 248, 203, 130, 182, 184, 113, 203, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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