Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eae9311ea476ec20b8ab1e5fb5a65185b7f1f94f4682d20bdb303207c0ce0ae

Tx prefix hash: 445d9fbda8008707721713504c93fa6a7b6d08156c05b04a56b9fa0bfaf7494e
Tx public key: e95f1ceefd6a2218f8e4f13d08eab77d32774b5dc7552fa10a0749580711c900
Timestamp: 1581474461 Timestamp [UCT]: 2020-02-12 02:27:41 Age [y:d:h:m:s]: 04:325:04:30:04
Block: 63146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124557 RingCT/type: yes/0
Extra: 01e95f1ceefd6a2218f8e4f13d08eab77d32774b5dc7552fa10a0749580711c900021100000002d81c26c0000000000000000000

1 output(s) for total of 379.142875839000 dcy

stealth address amount amount idx
00: 40c67896a837bb2822b1e365d2a5b952aeee2dd0dc770a42bf447b6fd42ed65e 379.142875839000 116436 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": 63156, "vin": [ { "gen": { "height": 63146 } } ], "vout": [ { "amount": 379142875839, "target": { "key": "40c67896a837bb2822b1e365d2a5b952aeee2dd0dc770a42bf447b6fd42ed65e" } } ], "extra": [ 1, 233, 95, 28, 238, 253, 106, 34, 24, 248, 228, 241, 61, 8, 234, 183, 125, 50, 119, 75, 93, 199, 85, 47, 161, 10, 7, 73, 88, 7, 17, 201, 0, 2, 17, 0, 0, 0, 2, 216, 28, 38, 192, 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