Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9908871235fe9acfb7d55822b6c05b55b0ccbdc5f51f22c134f72ac1016bf52b

Tx prefix hash: eac145a4b9fb1b96527dfd831d2544219314d8d72fff2f070630d45167069667
Tx public key: 91bf82b9f35307f0791f9c36c12064d626b01ba1081dd4c532717df591a94b5f
Timestamp: 1745222877 Timestamp [UCT]: 2025-04-21 08:07:57 Age [y:d:h:m:s]: 00:198:14:01:47
Block: 1266145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139625 RingCT/type: yes/0
Extra: 0191bf82b9f35307f0791f9c36c12064d626b01ba1081dd4c532717df591a94b5f0211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c95ee54d1869372f0b347cdd764a0c8c7cd505f8b8bb7b7183e392e59484cb4 0.600000000000 1753362 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": 1266155, "vin": [ { "gen": { "height": 1266145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c95ee54d1869372f0b347cdd764a0c8c7cd505f8b8bb7b7183e392e59484cb4" } } ], "extra": [ 1, 145, 191, 130, 185, 243, 83, 7, 240, 121, 31, 156, 54, 193, 32, 100, 214, 38, 176, 27, 161, 8, 29, 212, 197, 50, 113, 125, 245, 145, 169, 75, 95, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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