Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42a27e82c6dfb5e3d6b70f24f9707b993c9e105ec9fb60cb0d33d6cf2c0b4a0c

Tx prefix hash: 9d4d9a6437cecedac55b4dae5fe930816b96012ab38f0bfae02fe2c9d0613e1a
Tx public key: cf377fe444958928a5ecc7352c071c8c891a7cbf17cdbf420aaecf9dd6f88057
Timestamp: 1582390672 Timestamp [UCT]: 2020-02-22 16:57:52 Age [y:d:h:m:s]: 04:310:23:53:03
Block: 70379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114758 RingCT/type: yes/0
Extra: 01cf377fe444958928a5ecc7352c071c8c891a7cbf17cdbf420aaecf9dd6f88057021100000006d81c26c0000000000000000000

1 output(s) for total of 358.767806777000 dcy

stealth address amount amount idx
00: 3a8ccef2257a0b5ef59fb5794e8a03647ee405bfe0cfede269f37be06683e590 358.767806777000 129992 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": 70389, "vin": [ { "gen": { "height": 70379 } } ], "vout": [ { "amount": 358767806777, "target": { "key": "3a8ccef2257a0b5ef59fb5794e8a03647ee405bfe0cfede269f37be06683e590" } } ], "extra": [ 1, 207, 55, 127, 228, 68, 149, 137, 40, 165, 236, 199, 53, 44, 7, 28, 140, 137, 26, 124, 191, 23, 205, 191, 66, 10, 174, 207, 157, 214, 248, 128, 87, 2, 17, 0, 0, 0, 6, 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