Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d704723fee8d64c6178ae4f24b0f5c1e462d180da1cba549a890c07bb33246e8

Tx prefix hash: af9561cf4f2d803c1b46422ace0de257e21dce6fba774d060ed9d6eae1e87950
Tx public key: 592fb11048e4f4cf65deee3333f55d74cac7b2863f2756a122a593dbc0cdda7b
Timestamp: 1721547952 Timestamp [UCT]: 2024-07-21 07:45:52 Age [y:d:h:m:s]: 01:123:17:02:37
Block: 1070385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346928 RingCT/type: yes/0
Extra: 01592fb11048e4f4cf65deee3333f55d74cac7b2863f2756a122a593dbc0cdda7b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bdaf5ea264e6249bfdbe085e5d8a2b0e6333f6672b32f27c317db68821050db 0.600000000000 1542196 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": 1070395, "vin": [ { "gen": { "height": 1070385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bdaf5ea264e6249bfdbe085e5d8a2b0e6333f6672b32f27c317db68821050db" } } ], "extra": [ 1, 89, 47, 177, 16, 72, 228, 244, 207, 101, 222, 238, 51, 51, 245, 93, 116, 202, 199, 178, 134, 63, 39, 86, 161, 34, 165, 147, 219, 192, 205, 218, 123, 2, 17, 0, 0, 0, 3, 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