Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 922b7c9e2c0edfa3a95e87f0dbe43a5e56abee34d757bd9cf6e8487ab362c862

Tx prefix hash: 5e3ece4472d9739e7394e3a5a5a1c15dcd25cf4e8ab048e9e0ea38da92d692b8
Tx public key: 9b2a11e5d1a3e643797b80ccebbc6a43a7e9cd17494136a6c0a5298e6db17274
Timestamp: 1724461829 Timestamp [UCT]: 2024-08-24 01:10:29 Age [y:d:h:m:s]: 00:093:01:20:53
Block: 1094568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66535 RingCT/type: yes/0
Extra: 019b2a11e5d1a3e643797b80ccebbc6a43a7e9cd17494136a6c0a5298e6db17274021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4af5b70ce07e45f8349008758a0b605e332f107edc64ec51b5ae223c285e3cfd 0.600000000000 1569685 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": 1094578, "vin": [ { "gen": { "height": 1094568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4af5b70ce07e45f8349008758a0b605e332f107edc64ec51b5ae223c285e3cfd" } } ], "extra": [ 1, 155, 42, 17, 229, 209, 163, 230, 67, 121, 123, 128, 204, 235, 188, 106, 67, 167, 233, 205, 23, 73, 65, 54, 166, 192, 165, 41, 142, 109, 177, 114, 116, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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