Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0c898944e7b3c918a6b7fab9c43b4ce003bfe285edb7c9cc772cf7ddf83fd50

Tx prefix hash: c2b9123f38bb8187367d1ac06d59508b40e3d8f782a4303daeb974f77d23a77f
Tx public key: 8f84508956360261fe9c138c461d8d4e8d4ec79083132d3d5c171e41b7c2909e
Timestamp: 1730101345 Timestamp [UCT]: 2024-10-28 07:42:25 Age [y:d:h:m:s]: 00:159:06:13:53
Block: 1141227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113653 RingCT/type: yes/0
Extra: 018f84508956360261fe9c138c461d8d4e8d4ec79083132d3d5c171e41b7c2909e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e8e32c3283800a54f208b2714e292ddf0975bb2d1fe7f15da81a8f57cad0f07 0.600000000000 1625034 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": 1141237, "vin": [ { "gen": { "height": 1141227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e8e32c3283800a54f208b2714e292ddf0975bb2d1fe7f15da81a8f57cad0f07" } } ], "extra": [ 1, 143, 132, 80, 137, 86, 54, 2, 97, 254, 156, 19, 140, 70, 29, 141, 78, 141, 78, 199, 144, 131, 19, 45, 61, 92, 23, 30, 65, 183, 194, 144, 158, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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