Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b934e147109baa9d3a8a9fa2cee79759e1207892edb7bd34eff1456d5b24afa

Tx prefix hash: c95e70a5b913e2e673b511e750ebf39221aa8b3425e475edf84a6152a0b444d1
Tx public key: 1540872e2477bcf39df2f30c98faeb7933eff6fc79d46e1e96d370df23dd03ae
Timestamp: 1702722229 Timestamp [UCT]: 2023-12-16 10:23:49 Age [y:d:h:m:s]: 01:329:15:49:34
Block: 914313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494460 RingCT/type: yes/0
Extra: 011540872e2477bcf39df2f30c98faeb7933eff6fc79d46e1e96d370df23dd03ae02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 555f578c6b424b7fce493c2a873c972e0601d7c8145a595f181179eeb60dbcf7 0.600000000000 1371619 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": 914323, "vin": [ { "gen": { "height": 914313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "555f578c6b424b7fce493c2a873c972e0601d7c8145a595f181179eeb60dbcf7" } } ], "extra": [ 1, 21, 64, 135, 46, 36, 119, 188, 243, 157, 242, 243, 12, 152, 250, 235, 121, 51, 239, 246, 252, 121, 212, 110, 30, 150, 211, 112, 223, 35, 221, 3, 174, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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