Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9f690631acf6225ca41eb94446a51e7bec54579cf6b49e74ee6605665ba52ac

Tx prefix hash: afcd9dd0c94f54ddf7d3ee0bbb86f32e07f29b5728adbfc4bf32be44e7349f9e
Tx public key: 78fd3c6cd250ec2e4840ea5a10b0e4d93d6d8f312dfd3c80b33fa7a5dd52704f
Timestamp: 1580781285 Timestamp [UCT]: 2020-02-04 01:54:45 Age [y:d:h:m:s]: 04:328:17:31:47
Block: 57976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126521 RingCT/type: yes/0
Extra: 0178fd3c6cd250ec2e4840ea5a10b0e4d93d6d8f312dfd3c80b33fa7a5dd52704f02110000000c4943cd9f000000000000000000

1 output(s) for total of 394.368543341000 dcy

stealth address amount amount idx
00: 6f54bcd0a9c3b62027940304c7e12eef08ed7383bd7cbbfe43f67e841dd364ed 394.368543341000 107235 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": 57986, "vin": [ { "gen": { "height": 57976 } } ], "vout": [ { "amount": 394368543341, "target": { "key": "6f54bcd0a9c3b62027940304c7e12eef08ed7383bd7cbbfe43f67e841dd364ed" } } ], "extra": [ 1, 120, 253, 60, 108, 210, 80, 236, 46, 72, 64, 234, 90, 16, 176, 228, 217, 61, 109, 143, 49, 45, 253, 60, 128, 179, 63, 167, 165, 221, 82, 112, 79, 2, 17, 0, 0, 0, 12, 73, 67, 205, 159, 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