Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3edc8db5b707206b90d6e0b1443dea0f705f586cce05c0a0d89f930555db6899

Tx prefix hash: 0ecde1d12cda7c7f5d7eb1f6db8c29d78505f9b86b1c99ec51e603dbe45bb7c9
Tx public key: 8bf4fca1ef2a02311808d99ada7927c78376ca5ddb995af9c8ed3c8b3044cad7
Timestamp: 1723414510 Timestamp [UCT]: 2024-08-11 22:15:10 Age [y:d:h:m:s]: 00:238:03:26:18
Block: 1085859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170076 RingCT/type: yes/0
Extra: 018bf4fca1ef2a02311808d99ada7927c78376ca5ddb995af9c8ed3c8b3044cad7021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37edebc9e1cbe883be9c49e6ed828ebd1d046503a8aeb234cf58770a3331cbd0 0.600000000000 1560450 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": 1085869, "vin": [ { "gen": { "height": 1085859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37edebc9e1cbe883be9c49e6ed828ebd1d046503a8aeb234cf58770a3331cbd0" } } ], "extra": [ 1, 139, 244, 252, 161, 239, 42, 2, 49, 24, 8, 217, 154, 218, 121, 39, 199, 131, 118, 202, 93, 219, 153, 90, 249, 200, 237, 60, 139, 48, 68, 202, 215, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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