Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccbad3fef339097b8ab472b43fc74df48c54bb14c66df15ec0f4b6a6a977ae41

Tx prefix hash: 104046a5a3c6f53d75d065cb1bce817aa06a513505f0e92f2f20c980c3e58687
Tx public key: 0686b0316a1886e86ba8396d1a004905b26251bdd15a5aa0cb2358657c8ce6d8
Timestamp: 1627213691 Timestamp [UCT]: 2021-07-25 11:48:11 Age [y:d:h:m:s]: 03:126:20:02:44
Block: 300722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 862687 RingCT/type: yes/0
Extra: 010686b0316a1886e86ba8396d1a004905b26251bdd15a5aa0cb2358657c8ce6d8021100000037cc5ba4a5000000000000000000

1 output(s) for total of 61.884753842000 dcy

stealth address amount amount idx
00: 36903ec25fff74d2ccabc6e20b736f384d9e7e8713b75b2bf6608f31bb76b6e7 61.884753842000 628261 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": 300732, "vin": [ { "gen": { "height": 300722 } } ], "vout": [ { "amount": 61884753842, "target": { "key": "36903ec25fff74d2ccabc6e20b736f384d9e7e8713b75b2bf6608f31bb76b6e7" } } ], "extra": [ 1, 6, 134, 176, 49, 106, 24, 134, 232, 107, 168, 57, 109, 26, 0, 73, 5, 178, 98, 81, 189, 209, 90, 90, 160, 203, 35, 88, 101, 124, 140, 230, 216, 2, 17, 0, 0, 0, 55, 204, 91, 164, 165, 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