Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21d96ad168e6d14ce6b59022f76fc2a9f1ef7ac69dca68e51fd0375be3950e40

Tx prefix hash: 9b628dcb8ee7587867f855299f5f69083f0d6eb88cd7cd5da0adc58765c84b31
Tx public key: bbfb5dc7436f5851e207ae5c82e5bc4744322709336a868b05942e82d1aad256
Timestamp: 1707002407 Timestamp [UCT]: 2024-02-03 23:20:07 Age [y:d:h:m:s]: 01:278:18:14:31
Block: 949783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458014 RingCT/type: yes/0
Extra: 01bbfb5dc7436f5851e207ae5c82e5bc4744322709336a868b05942e82d1aad25602110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b623b73590d58abde70135cffe7e65ef370e0b9c114fb139ee4f1a6a5f413f34 0.600000000000 1408315 of 15

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": 949793, "vin": [ { "gen": { "height": 949783 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b623b73590d58abde70135cffe7e65ef370e0b9c114fb139ee4f1a6a5f413f34" } } ], "extra": [ 1, 187, 251, 93, 199, 67, 111, 88, 81, 226, 7, 174, 92, 130, 229, 188, 71, 68, 50, 39, 9, 51, 106, 134, 139, 5, 148, 46, 130, 209, 170, 210, 86, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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