Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fed1d18f0c51cbb25927fa8318f367edd6691bfc579f288bd044b07b15681bf7

Tx prefix hash: 91800915bcb83237891d745fd7befad1b16a2526b8b1f5bf490e76cca2f3698d
Tx public key: 3e0e72ca5b6b19d6cf63a42d4bdb79799dc7c6a0e6e31e281151dbfdf4c3e8ca
Timestamp: 1735406631 Timestamp [UCT]: 2024-12-28 17:23:51 Age [y:d:h:m:s]: 00:093:00:25:57
Block: 1185152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66266 RingCT/type: yes/0
Extra: 013e0e72ca5b6b19d6cf63a42d4bdb79799dc7c6a0e6e31e281151dbfdf4c3e8ca0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6db1c705965267686b685bf738b2164c6c99c250d3508d0fdc8b3ed2d5bf8b40 0.600000000000 1671617 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": 1185162, "vin": [ { "gen": { "height": 1185152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6db1c705965267686b685bf738b2164c6c99c250d3508d0fdc8b3ed2d5bf8b40" } } ], "extra": [ 1, 62, 14, 114, 202, 91, 107, 25, 214, 207, 99, 164, 45, 75, 219, 121, 121, 157, 199, 198, 160, 230, 227, 30, 40, 17, 81, 219, 253, 244, 195, 232, 202, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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