Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbd2e2a3e898b2fbf417c8bd4d06de00c6df7a25b3e057497213a6619b17519e

Tx prefix hash: 3e982346d7dca536e2d172a1693a304c987eaeda9e778c012998cfcef1fa79d2
Tx public key: 508b23072c9cc66cf179e856e3f9ec89eb0cff861a36856fd066f171c9a7bcaa
Timestamp: 1725291930 Timestamp [UCT]: 2024-09-02 15:45:30 Age [y:d:h:m:s]: 00:083:06:51:07
Block: 1101430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59557 RingCT/type: yes/0
Extra: 01508b23072c9cc66cf179e856e3f9ec89eb0cff861a36856fd066f171c9a7bcaa021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84c254c94b57810d3cc0350be44fcadbd39bcd67c4a755303cb96dff1ab29d83 0.600000000000 1577475 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": 1101440, "vin": [ { "gen": { "height": 1101430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c254c94b57810d3cc0350be44fcadbd39bcd67c4a755303cb96dff1ab29d83" } } ], "extra": [ 1, 80, 139, 35, 7, 44, 156, 198, 108, 241, 121, 232, 86, 227, 249, 236, 137, 235, 12, 255, 134, 26, 54, 133, 111, 208, 102, 241, 113, 201, 167, 188, 170, 2, 17, 0, 0, 0, 5, 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