Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb73f4289442e61526561f3fff4dba06cb3303058bd1efcd4e23dfd0d39b5eb9

Tx prefix hash: 298319695554291562f0e179a1f704e2f1cef68a6248e9f195c87058c2335439
Tx public key: e554312816db38ade44a17f37dadb3b4de759772bd5fc554ae0a04d94b52cb1a
Timestamp: 1604860765 Timestamp [UCT]: 2020-11-08 18:39:25 Age [y:d:h:m:s]: 04:183:19:27:11
Block: 147567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1132353 RingCT/type: yes/0
Extra: 01e554312816db38ade44a17f37dadb3b4de759772bd5fc554ae0a04d94b52cb1a021100000034f8cbd8e0000000000000000000

1 output(s) for total of 199.090239210000 dcy

stealth address amount amount idx
00: 050ea0490b3cdb313d92aa28b789de74c5f2d9828c2d6e869345a95716f0ddd3 199.090239210000 245235 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": 147577, "vin": [ { "gen": { "height": 147567 } } ], "vout": [ { "amount": 199090239210, "target": { "key": "050ea0490b3cdb313d92aa28b789de74c5f2d9828c2d6e869345a95716f0ddd3" } } ], "extra": [ 1, 229, 84, 49, 40, 22, 219, 56, 173, 228, 74, 23, 243, 125, 173, 179, 180, 222, 117, 151, 114, 189, 95, 197, 84, 174, 10, 4, 217, 75, 82, 203, 26, 2, 17, 0, 0, 0, 52, 248, 203, 216, 224, 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