Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862ebe52f8228c70037ab688b9b1f986866463192a31e868b5b8be95c0ddae00

Tx prefix hash: 399dec1efbf568f9efc86fac10b13a856d4ccd270deb5953c3652f11d8dff620
Tx public key: a5f55b14cf5b4e751c672f1dae03f77dc3f12a59fbfae85987639d05c24c1af3
Timestamp: 1743605498 Timestamp [UCT]: 2025-04-02 14:51:38 Age [y:d:h:m:s]: 00:265:13:51:45
Block: 1252768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187582 RingCT/type: yes/0
Extra: 01a5f55b14cf5b4e751c672f1dae03f77dc3f12a59fbfae85987639d05c24c1af30211000000024060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b5cb5a887eb5c7f9d4dca57bb44856e26e7d83db47f9623281ea82f78e35d44 0.600000000000 1739849 of 15

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": 1252778, "vin": [ { "gen": { "height": 1252768 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b5cb5a887eb5c7f9d4dca57bb44856e26e7d83db47f9623281ea82f78e35d44" } } ], "extra": [ 1, 165, 245, 91, 20, 207, 91, 78, 117, 28, 103, 47, 29, 174, 3, 247, 125, 195, 241, 42, 89, 251, 250, 232, 89, 135, 99, 157, 5, 194, 76, 26, 243, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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