Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bf5ab65b452aa75d8f0051eea444728b861932758b153d5d860f8124221c1e9

Tx prefix hash: aa3ea088dddf8b506006aa60edc187d6e1a2a83c2f8f5fbb54fb8c6b165583da
Tx public key: 0b6fed7ee7bd38ab848d3f0cd75cfa2927dbfd18ed47ca7c7eabd04db783bf3d
Timestamp: 1609262267 Timestamp [UCT]: 2020-12-29 17:17:47 Age [y:d:h:m:s]: 04:000:14:13:06
Block: 171538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1014028 RingCT/type: yes/0
Extra: 010b6fed7ee7bd38ab848d3f0cd75cfa2927dbfd18ed47ca7c7eabd04db783bf3d021100000ac54ea414e5000000000000000000

1 output(s) for total of 165.815093721000 dcy

stealth address amount amount idx
00: 4c2abd9a17d0f6ff1c235c789176cc779e1c422f4ab17be6c45f1d41443499f5 165.815093721000 323197 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": 171548, "vin": [ { "gen": { "height": 171538 } } ], "vout": [ { "amount": 165815093721, "target": { "key": "4c2abd9a17d0f6ff1c235c789176cc779e1c422f4ab17be6c45f1d41443499f5" } } ], "extra": [ 1, 11, 111, 237, 126, 231, 189, 56, 171, 132, 141, 63, 12, 215, 92, 250, 41, 39, 219, 253, 24, 237, 71, 202, 124, 126, 171, 208, 77, 183, 131, 191, 61, 2, 17, 0, 0, 10, 197, 78, 164, 20, 229, 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