Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cafef32e01703cbc922372cbe5d56993c8ac6ea591184957a2b06b0b724fb8d

Tx prefix hash: 676a8f791b4bc6ad59225669ffe02351d838f59ae9e4a84f91210234c175a13f
Tx public key: e698977f22eafc207d9d8358e57f142f16ae651474424c9bce6c1391622c226f
Timestamp: 1634819726 Timestamp [UCT]: 2021-10-21 12:35:26 Age [y:d:h:m:s]: 03:068:23:55:24
Block: 357452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827555 RingCT/type: yes/0
Extra: 01e698977f22eafc207d9d8358e57f142f16ae651474424c9bce6c1391622c226f02110000000137cb3088000000000000000000

1 output(s) for total of 40.144484394000 dcy

stealth address amount amount idx
00: 0cd8d16ff36dc6604d5090860bd55d0538a47b0141840daf2b17b42a828186f2 40.144484394000 728870 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": 357462, "vin": [ { "gen": { "height": 357452 } } ], "vout": [ { "amount": 40144484394, "target": { "key": "0cd8d16ff36dc6604d5090860bd55d0538a47b0141840daf2b17b42a828186f2" } } ], "extra": [ 1, 230, 152, 151, 127, 34, 234, 252, 32, 125, 157, 131, 88, 229, 127, 20, 47, 22, 174, 101, 20, 116, 66, 76, 155, 206, 108, 19, 145, 98, 44, 34, 111, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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