Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f7bc6a4c1190de8c57cee28b11cdd3803867e7a34c2f79f4d386242d79707f

Tx prefix hash: 220d9f29de6695b488fc4b636676d636976513f6e2bbf1eafe74dcbe113da14d
Tx public key: 58d77c8f82e50bd29e2b2dff8c81774d926bf5961c1fc1827c6aa77ef74e29a2
Timestamp: 1578642935 Timestamp [UCT]: 2020-01-10 07:55:35 Age [y:d:h:m:s]: 04:321:14:35:15
Block: 42358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119341 RingCT/type: yes/0
Extra: 0158d77c8f82e50bd29e2b2dff8c81774d926bf5961c1fc1827c6aa77ef74e29a20211000000088a2ee0d9000000000000000000

1 output(s) for total of 444.274315616000 dcy

stealth address amount amount idx
00: 893006023b828874a1a02d4d264b74fc720fd7bda7c8917fcb2cb19949fe6622 444.274315616000 76270 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": 42368, "vin": [ { "gen": { "height": 42358 } } ], "vout": [ { "amount": 444274315616, "target": { "key": "893006023b828874a1a02d4d264b74fc720fd7bda7c8917fcb2cb19949fe6622" } } ], "extra": [ 1, 88, 215, 124, 143, 130, 229, 11, 210, 158, 43, 45, 255, 140, 129, 119, 77, 146, 107, 245, 150, 28, 31, 193, 130, 124, 106, 167, 126, 247, 78, 41, 162, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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