Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f318e81d9eafd3313720cdb22d5520cd5f65a5711bea252aae2b732b9cce9f8

Tx prefix hash: 5646f5e534c742973b1ca6d906cf32d97bb6fddd6142e0b93f7f7466825ac926
Tx public key: f53d7bab02c5d6f66a643302e83067b6885ef6e9a3cf2bd4ab0da39f3e001304
Timestamp: 1583854994 Timestamp [UCT]: 2020-03-10 15:43:14 Age [y:d:h:m:s]: 04:297:11:12:17
Block: 79874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107707 RingCT/type: yes/0
Extra: 01f53d7bab02c5d6f66a643302e83067b6885ef6e9a3cf2bd4ab0da39f3e00130402110000000a3b1b9791000000000000000000

1 output(s) for total of 333.691443667000 dcy

stealth address amount amount idx
00: 1f62eb55c8fb3c06c11ee82cff3dd07374e4c7cd0045c4521c668a9392d19529 333.691443667000 146154 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": 79884, "vin": [ { "gen": { "height": 79874 } } ], "vout": [ { "amount": 333691443667, "target": { "key": "1f62eb55c8fb3c06c11ee82cff3dd07374e4c7cd0045c4521c668a9392d19529" } } ], "extra": [ 1, 245, 61, 123, 171, 2, 197, 214, 246, 106, 100, 51, 2, 232, 48, 103, 182, 136, 94, 246, 233, 163, 207, 43, 212, 171, 13, 163, 159, 62, 0, 19, 4, 2, 17, 0, 0, 0, 10, 59, 27, 151, 145, 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