Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299f60f9d227542fe44dedc5b5b6ec94d093cef91f6a0a57a37deea84e4fb4e5

Tx prefix hash: b09afe70d82c304e619b789a6621c96757a701b3a48ffc993e13d8ec48de5f39
Tx public key: cdfe8563c2160bdf23a2d51bc7f3ab277541855614a635442a8c03c8fbdf3a18
Timestamp: 1763800752 Timestamp [UCT]: 2025-11-22 08:39:12 Age [y:d:h:m:s]: 00:036:08:06:54
Block: 1417541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26035 RingCT/type: yes/0
Extra: 01cdfe8563c2160bdf23a2d51bc7f3ab277541855614a635442a8c03c8fbdf3a18021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844330e766a52adfad087800e05e2abdfd1575ef5a91df7bcbc8382dfda0f782 0.600000000000 1906064 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": 1417551, "vin": [ { "gen": { "height": 1417541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844330e766a52adfad087800e05e2abdfd1575ef5a91df7bcbc8382dfda0f782" } } ], "extra": [ 1, 205, 254, 133, 99, 194, 22, 11, 223, 35, 162, 213, 27, 199, 243, 171, 39, 117, 65, 133, 86, 20, 166, 53, 68, 42, 140, 3, 200, 251, 223, 58, 24, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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