Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc4ca6fc4a7aa0d8d222e89f7e75de34de7cd7879dfc0a526b6c8e2a15bbd5f8

Tx prefix hash: 45c0bac797b68bfecaf95e0be6a63daaa105f058fc2b409412c23a2785c9b110
Tx public key: 10ba3b10492a4b6401859613c1240579b9bbc113d03f1a2df076bb1eef979f4e
Timestamp: 1580817101 Timestamp [UCT]: 2020-02-04 11:51:41 Age [y:d:h:m:s]: 04:346:11:52:46
Block: 58614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138884 RingCT/type: yes/0
Extra: 0110ba3b10492a4b6401859613c1240579b9bbc113d03f1a2df076bb1eef979f4e021100000058d81c26c0000000000000000000

1 output(s) for total of 392.453590318000 dcy

stealth address amount amount idx
00: 8f010aad0c259de106ed79a20fb1e2b1f92399a7cb5e9e128508689f2c7f9184 392.453590318000 108284 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": 58624, "vin": [ { "gen": { "height": 58614 } } ], "vout": [ { "amount": 392453590318, "target": { "key": "8f010aad0c259de106ed79a20fb1e2b1f92399a7cb5e9e128508689f2c7f9184" } } ], "extra": [ 1, 16, 186, 59, 16, 73, 42, 75, 100, 1, 133, 150, 19, 193, 36, 5, 121, 185, 187, 193, 19, 208, 63, 26, 45, 240, 118, 187, 30, 239, 151, 159, 78, 2, 17, 0, 0, 0, 88, 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