Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439a0404392e5d70eb63f49170427f02ed6f72d6c2499126cd4f75de1fc57154

Tx prefix hash: 36217a5d8c57ec12809e2ef414340923dd4fa1bcd3cc5997aae44d17e7972386
Tx public key: 609ba38eb1e5c9752b945bca464b9ca6f0c0c0ff18649e3b8b0bc6214007b431
Timestamp: 1684332236 Timestamp [UCT]: 2023-05-17 14:03:56 Age [y:d:h:m:s]: 01:249:11:35:36
Block: 762099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439714 RingCT/type: yes/0
Extra: 01609ba38eb1e5c9752b945bca464b9ca6f0c0c0ff18649e3b8b0bc6214007b431021100000002faf35c9c000000000000000000

1 output(s) for total of 1.831680981000 dcy

stealth address amount amount idx
00: d3bdaabd5df9499c89bf83a790711902c27a0bec6d9a2e8e45a6947fcb423f80 1.831680981000 1210812 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": 762109, "vin": [ { "gen": { "height": 762099 } } ], "vout": [ { "amount": 1831680981, "target": { "key": "d3bdaabd5df9499c89bf83a790711902c27a0bec6d9a2e8e45a6947fcb423f80" } } ], "extra": [ 1, 96, 155, 163, 142, 177, 229, 201, 117, 43, 148, 91, 202, 70, 75, 156, 166, 240, 192, 192, 255, 24, 100, 158, 59, 139, 11, 198, 33, 64, 7, 180, 49, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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