Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f44ac36e59d4e73e8ae16956e5144f7521c9f9a15a401e5158c2bfab233df8

Tx prefix hash: 601b7496b583f10ac75f0df4c30bfd15806f786d2ca9696da0e3063f28d6a0ac
Tx public key: 69016adc65ece2728362df888fb6eba45a6b65bf141581a170cc67d0020275b4
Timestamp: 1578078667 Timestamp [UCT]: 2020-01-03 19:11:07 Age [y:d:h:m:s]: 04:333:15:01:13
Block: 37926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127713 RingCT/type: yes/0
Extra: 0169016adc65ece2728362df888fb6eba45a6b65bf141581a170cc67d0020275b402110000000cd81c26c0000000000000000000

1 output(s) for total of 459.626871858000 dcy

stealth address amount amount idx
00: cd211aa89db328b79df9ab65c664f64c3e0ea731572f23ac19a2e5186af8fa88 459.626871858000 64483 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": 37936, "vin": [ { "gen": { "height": 37926 } } ], "vout": [ { "amount": 459626871858, "target": { "key": "cd211aa89db328b79df9ab65c664f64c3e0ea731572f23ac19a2e5186af8fa88" } } ], "extra": [ 1, 105, 1, 106, 220, 101, 236, 226, 114, 131, 98, 223, 136, 143, 182, 235, 164, 90, 107, 101, 191, 20, 21, 129, 161, 112, 204, 103, 208, 2, 2, 117, 180, 2, 17, 0, 0, 0, 12, 216, 28, 38, 192, 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