Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 414b22f995424f497c0b207f4ad1d69623d9ce391b36ad181a05a61b3723378c

Tx prefix hash: 7b26888bfe79a0781fb9ebaa7dd3bbf4fb82bb411b8d0859d02be201f25aadca
Tx public key: 5e3c2a4ae2f338b9fea5552ae483d0030a8f5f2a1e8515a106eb444e15ecd934
Timestamp: 1580977920 Timestamp [UCT]: 2020-02-06 08:32:00 Age [y:d:h:m:s]: 05:128:16:46:27
Block: 59754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244060 RingCT/type: yes/0
Extra: 015e3c2a4ae2f338b9fea5552ae483d0030a8f5f2a1e8515a106eb444e15ecd934021100000002026b59f3000000000000000000

1 output(s) for total of 389.055009439000 dcy

stealth address amount amount idx
00: e43b2ea8cc4ccd526e5c2b7a117b612979cc2afe4f7bc646d7ed5964648fae4a 389.055009439000 110256 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": 59764, "vin": [ { "gen": { "height": 59754 } } ], "vout": [ { "amount": 389055009439, "target": { "key": "e43b2ea8cc4ccd526e5c2b7a117b612979cc2afe4f7bc646d7ed5964648fae4a" } } ], "extra": [ 1, 94, 60, 42, 74, 226, 243, 56, 185, 254, 165, 85, 42, 228, 131, 208, 3, 10, 143, 95, 42, 30, 133, 21, 161, 6, 235, 68, 78, 21, 236, 217, 52, 2, 17, 0, 0, 0, 2, 2, 107, 89, 243, 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