Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 209f443e057c47980d7b59621a020bf0d4a4f90dcc0d8286c3bbe4e2bbef1fdc

Tx prefix hash: 4b613d2b1446069eb2e01f92ed5e11732f101e0b8bc95731796f2e6e1459f0f3
Tx public key: dfcc37149eace844d7a46b10eb2f1b6ee8ad0aa1d2399357aea9b26b22e4bdaa
Timestamp: 1645239942 Timestamp [UCT]: 2022-02-19 03:05:42 Age [y:d:h:m:s]: 02:260:16:38:30
Block: 441629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 705672 RingCT/type: yes/0
Extra: 01dfcc37149eace844d7a46b10eb2f1b6ee8ad0aa1d2399357aea9b26b22e4bdaa021100000001a272b9cb000000000000000000

1 output(s) for total of 21.120300114000 dcy

stealth address amount amount idx
00: b41093c4572edb8ae9afd91dbac1541026e73991cd12d633cc4555a9653825ad 21.120300114000 854230 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": 441639, "vin": [ { "gen": { "height": 441629 } } ], "vout": [ { "amount": 21120300114, "target": { "key": "b41093c4572edb8ae9afd91dbac1541026e73991cd12d633cc4555a9653825ad" } } ], "extra": [ 1, 223, 204, 55, 20, 158, 172, 232, 68, 215, 164, 107, 16, 235, 47, 27, 110, 232, 173, 10, 161, 210, 57, 147, 87, 174, 169, 178, 107, 34, 228, 189, 170, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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