Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7cca67eefc66d88ede0968bdbaf5652288bf4a06924dc6a6ca409f306767515

Tx prefix hash: 43368f89aaeadbcc80533703c3a059f72e6bc5b13e8d0057091e8047186c9d99
Tx public key: a9336449d0f4d69c50aae371538e276a90f4d0a95854d842b57912c70606894c
Timestamp: 1638671407 Timestamp [UCT]: 2021-12-05 02:30:07 Age [y:d:h:m:s]: 03:066:15:52:34
Block: 388642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 826323 RingCT/type: yes/0
Extra: 01a9336449d0f4d69c50aae371538e276a90f4d0a95854d842b57912c70606894c02110000002de9564d6f000000000000000000

1 output(s) for total of 31.643203303000 dcy

stealth address amount amount idx
00: 600d37de6ddb1944476dc8af4a8d4cb44b6b1db9eb5459d89ca574cf08c1fe3b 31.643203303000 783403 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": 388652, "vin": [ { "gen": { "height": 388642 } } ], "vout": [ { "amount": 31643203303, "target": { "key": "600d37de6ddb1944476dc8af4a8d4cb44b6b1db9eb5459d89ca574cf08c1fe3b" } } ], "extra": [ 1, 169, 51, 100, 73, 208, 244, 214, 156, 80, 170, 227, 113, 83, 142, 39, 106, 144, 244, 208, 169, 88, 84, 216, 66, 181, 121, 18, 199, 6, 6, 137, 76, 2, 17, 0, 0, 0, 45, 233, 86, 77, 111, 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