Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37c8160a6373225d55c29a1a2628ee7bd1a8f37e54c4dd0979ea6906807158b2

Tx prefix hash: a3077927a7a9d4b54facd3654f141ff9ad92f62eba4cf34e8d09d46c2880162a
Tx public key: 8fa0c210f755c8a4858fc5181fc7ceb1e95b7d8e4588d550ebba45650e959d56
Timestamp: 1735681806 Timestamp [UCT]: 2024-12-31 21:50:06 Age [y:d:h:m:s]: 01:006:16:22:03
Block: 1187433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263230 RingCT/type: yes/0
Extra: 018fa0c210f755c8a4858fc5181fc7ceb1e95b7d8e4588d550ebba45650e959d560211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 238c20a1846dff4ecc1fc9c095082a3a37cc91d07535d0cd67423a44770dc2b9 0.600000000000 1673924 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": 1187443, "vin": [ { "gen": { "height": 1187433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "238c20a1846dff4ecc1fc9c095082a3a37cc91d07535d0cd67423a44770dc2b9" } } ], "extra": [ 1, 143, 160, 194, 16, 247, 85, 200, 164, 133, 143, 197, 24, 31, 199, 206, 177, 233, 91, 125, 142, 69, 136, 213, 80, 235, 186, 69, 101, 14, 149, 157, 86, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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