Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86cd722ed580dd974b5e19fdc4a7864bdaa8aae5f237492a77e3e7ec934758b8

Tx prefix hash: bf64b0d3a5b27ae4016d30d3e288eb77a6f348d859721b4aa8ea38934ee5b1db
Tx public key: 3137f23fe1957db1b85ea8d29bbaf3652023d201052ebe91917b51d9afcf9206
Timestamp: 1735132660 Timestamp [UCT]: 2024-12-25 13:17:40 Age [y:d:h:m:s]: 00:099:07:04:47
Block: 1182899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70739 RingCT/type: yes/0
Extra: 013137f23fe1957db1b85ea8d29bbaf3652023d201052ebe91917b51d9afcf92060211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adb4f083e1e239218a8dc69d5b3d7d60293c3a83274182184ce4cbff547ebeb6 0.600000000000 1669338 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": 1182909, "vin": [ { "gen": { "height": 1182899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adb4f083e1e239218a8dc69d5b3d7d60293c3a83274182184ce4cbff547ebeb6" } } ], "extra": [ 1, 49, 55, 242, 63, 225, 149, 125, 177, 184, 94, 168, 210, 155, 186, 243, 101, 32, 35, 210, 1, 5, 46, 190, 145, 145, 123, 81, 217, 175, 207, 146, 6, 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