Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1179a10d7a7d9d371ddcc59f2ef9bf584c6740f9d79f4737f70123305e27bff1

Tx prefix hash: 090cc05973eba9e3b7a76e7d842ae99a78aa1b820b04ca15bf3ca951075213a5
Tx public key: 9127f5c8a4be00e318274fe03832ffc8e978dd794caa4e03af85d37c110346cb
Timestamp: 1715078937 Timestamp [UCT]: 2024-05-07 10:48:57 Age [y:d:h:m:s]: 00:345:18:34:39
Block: 1016765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247162 RingCT/type: yes/0
Extra: 019127f5c8a4be00e318274fe03832ffc8e978dd794caa4e03af85d37c110346cb02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62b87cc30538080ceeba21a7d26e541ba05266e37fdce268f178d091021001f3 0.600000000000 1480442 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": 1016775, "vin": [ { "gen": { "height": 1016765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62b87cc30538080ceeba21a7d26e541ba05266e37fdce268f178d091021001f3" } } ], "extra": [ 1, 145, 39, 245, 200, 164, 190, 0, 227, 24, 39, 79, 224, 56, 50, 255, 200, 233, 120, 221, 121, 76, 170, 78, 3, 175, 133, 211, 124, 17, 3, 70, 203, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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