Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 874574822bede4c6d89472cd3745fa8ecf0d013217e2a61bc6c519de823b385a

Tx prefix hash: f61aa5c934573da4d8185e21560ccc6411aa6a39bb15f03e25ac4c2c4cd0b87d
Tx public key: de8685c778e583092f10baa861cde7e94896686d60190b5ff7beb8736844af8b
Timestamp: 1689619139 Timestamp [UCT]: 2023-07-17 18:38:59 Age [y:d:h:m:s]: 01:180:00:12:36
Block: 805944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389985 RingCT/type: yes/0
Extra: 01de8685c778e583092f10baa861cde7e94896686d60190b5ff7beb8736844af8b02110000000633af99f4000000000000000000

1 output(s) for total of 1.310910632000 dcy

stealth address amount amount idx
00: 4d9d58d4eaec71f32933e1fcce8b702914bdaa3dfd90222c3b2cbda67976f7ab 1.310910632000 1257239 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": 805954, "vin": [ { "gen": { "height": 805944 } } ], "vout": [ { "amount": 1310910632, "target": { "key": "4d9d58d4eaec71f32933e1fcce8b702914bdaa3dfd90222c3b2cbda67976f7ab" } } ], "extra": [ 1, 222, 134, 133, 199, 120, 229, 131, 9, 47, 16, 186, 168, 97, 205, 231, 233, 72, 150, 104, 109, 96, 25, 11, 95, 247, 190, 184, 115, 104, 68, 175, 139, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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