Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8422cd85ddf22175ff0218f7a2cbdca241a96f83eaa5e585514e55edbfdfff8

Tx prefix hash: 7b9056ae7fc96aae6800b76f51997e96b10f55c8bbeb41f78ff0bafd7ce5556f
Tx public key: 965f6aa4c99de832c1d1369b061e834f745467c83df9bd411af3327d2310b9a7
Timestamp: 1725133691 Timestamp [UCT]: 2024-08-31 19:48:11 Age [y:d:h:m:s]: 00:217:16:03:43
Block: 1100115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155420 RingCT/type: yes/0
Extra: 01965f6aa4c99de832c1d1369b061e834f745467c83df9bd411af3327d2310b9a702110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9647915121b0a0c8a8aea28085fecdbb65618bb9d15bf188614e4e2b4029a804 0.600000000000 1576088 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": 1100125, "vin": [ { "gen": { "height": 1100115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9647915121b0a0c8a8aea28085fecdbb65618bb9d15bf188614e4e2b4029a804" } } ], "extra": [ 1, 150, 95, 106, 164, 201, 157, 232, 50, 193, 209, 54, 155, 6, 30, 131, 79, 116, 84, 103, 200, 61, 249, 189, 65, 26, 243, 50, 125, 35, 16, 185, 167, 2, 17, 0, 0, 0, 11, 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