Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc9664e8e18fa0bad28c5bbff5624ceeb3bc57841ecad81679b4ed4cecb18aa

Tx prefix hash: 9fa423a13d18003554dabb6793ba903db68be26e2ea72603153e0176f2467e1f
Tx public key: bf443fa45e7ae26a74a2a5126e9bb7f15c447c4c2cf1502e1c4f1e66787cfd87
Timestamp: 1577169015 Timestamp [UCT]: 2019-12-24 06:30:15 Age [y:d:h:m:s]: 05:313:22:51:04
Block: 30445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1372001 RingCT/type: yes/0
Extra: 01bf443fa45e7ae26a74a2a5126e9bb7f15c447c4c2cf1502e1c4f1e66787cfd8702110000000e8a2ee0d9000000000000000000

1 output(s) for total of 486.551755664000 dcy

stealth address amount amount idx
00: 3b48351b02fa26c2fe9987d6aea4fb5aec2729f1477c6a58c5e532aba4e2f16b 486.551755664000 50267 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": 30455, "vin": [ { "gen": { "height": 30445 } } ], "vout": [ { "amount": 486551755664, "target": { "key": "3b48351b02fa26c2fe9987d6aea4fb5aec2729f1477c6a58c5e532aba4e2f16b" } } ], "extra": [ 1, 191, 68, 63, 164, 94, 122, 226, 106, 116, 162, 165, 18, 110, 155, 183, 241, 92, 68, 124, 76, 44, 241, 80, 46, 28, 79, 30, 102, 120, 124, 253, 135, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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