Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9285d5b1f90e232352503bb15bbdc174f718ee682b25d3eab7e8f41f947dc74a

Tx prefix hash: 59d09a34c8f624f72841d9774de3d3bd22d038b57ae0dc6bc1b0aa15cb2d2b6d
Tx public key: d526317b576441107dfa4f0894875040640392bafde0ab0e40f7835657b62b6e
Timestamp: 1649711274 Timestamp [UCT]: 2022-04-11 21:07:54 Age [y:d:h:m:s]: 02:348:15:37:15
Block: 478159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768821 RingCT/type: yes/0
Extra: 01d526317b576441107dfa4f0894875040640392bafde0ab0e40f7835657b62b6e021100000002a8c141c5000000000000000000

1 output(s) for total of 15.983098550000 dcy

stealth address amount amount idx
00: c4f67c65e7c411f86d5d45b17d5884b13ea0cb18fc69e998a1e873703f0ece2a 15.983098550000 898890 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": 478169, "vin": [ { "gen": { "height": 478159 } } ], "vout": [ { "amount": 15983098550, "target": { "key": "c4f67c65e7c411f86d5d45b17d5884b13ea0cb18fc69e998a1e873703f0ece2a" } } ], "extra": [ 1, 213, 38, 49, 123, 87, 100, 65, 16, 125, 250, 79, 8, 148, 135, 80, 64, 100, 3, 146, 186, 253, 224, 171, 14, 64, 247, 131, 86, 87, 182, 43, 110, 2, 17, 0, 0, 0, 2, 168, 193, 65, 197, 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