Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a42c07020658100c96a6c9e57b6a9cdfcacef532c65fe7eb2138355f4875f01b

Tx prefix hash: 881487e1e4dbc0deb45ee7f9da528cb5a9b80ee0627b44586273d2a91a051c25
Tx public key: 41fcfbe34bd1f21792df3d3c2e804ba498e41d87733490b47667fde56ea49058
Timestamp: 1683421165 Timestamp [UCT]: 2023-05-07 00:59:25 Age [y:d:h:m:s]: 02:019:01:05:17
Block: 754557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535748 RingCT/type: yes/0
Extra: 0141fcfbe34bd1f21792df3d3c2e804ba498e41d87733490b47667fde56ea49058021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.940169281000 dcy

stealth address amount amount idx
00: 21e7026e466805e3c3c207cd55988ff4ff1e0b6f905a5897ad4bf609e4f8af1a 1.940169281000 1202834 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": 754567, "vin": [ { "gen": { "height": 754557 } } ], "vout": [ { "amount": 1940169281, "target": { "key": "21e7026e466805e3c3c207cd55988ff4ff1e0b6f905a5897ad4bf609e4f8af1a" } } ], "extra": [ 1, 65, 252, 251, 227, 75, 209, 242, 23, 146, 223, 61, 60, 46, 128, 75, 164, 152, 228, 29, 135, 115, 52, 144, 180, 118, 103, 253, 229, 110, 164, 144, 88, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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