Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cee1addd77b87b0e4094562c66edc5acb2cf73f21a692071221da313d38d0564

Tx prefix hash: 567e711d73a4aee26ac52f86f3cd08abcafd435e85b4f58854efbd414999b1bd
Tx public key: 9635960bb162b2bfe4b8590b0bb38364c145fa1177d5751c77edc5edf35df240
Timestamp: 1578839569 Timestamp [UCT]: 2020-01-12 14:32:49 Age [y:d:h:m:s]: 04:319:18:15:54
Block: 44036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117973 RingCT/type: yes/0
Extra: 019635960bb162b2bfe4b8590b0bb38364c145fa1177d5751c77edc5edf35df240021100000001d81c26c0000000000000000000

1 output(s) for total of 438.622891471000 dcy

stealth address amount amount idx
00: a4cb613c9a7694ebd18b78ad3aeb79a028784a4cf30d2529c1c27163bbc014cd 438.622891471000 79997 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": 44046, "vin": [ { "gen": { "height": 44036 } } ], "vout": [ { "amount": 438622891471, "target": { "key": "a4cb613c9a7694ebd18b78ad3aeb79a028784a4cf30d2529c1c27163bbc014cd" } } ], "extra": [ 1, 150, 53, 150, 11, 177, 98, 178, 191, 228, 184, 89, 11, 11, 179, 131, 100, 193, 69, 250, 17, 119, 213, 117, 28, 119, 237, 197, 237, 243, 93, 242, 64, 2, 17, 0, 0, 0, 1, 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