Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59db17ee166dbbf83859e3778e06d013f70426a860537de6432e0a2df1444a9e

Tx prefix hash: 08182e5aeff4301a5fb10318cc4210d09efbeacf3bc600b671c7b6b3d71255a6
Tx public key: b638e8e54971f7a7c245a86cb2c847c23125cb4408aa4055ba19a4f58c921055
Timestamp: 1730763264 Timestamp [UCT]: 2024-11-04 23:34:24 Age [y:d:h:m:s]: 00:078:09:18:40
Block: 1146698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56042 RingCT/type: yes/0
Extra: 01b638e8e54971f7a7c245a86cb2c847c23125cb4408aa4055ba19a4f58c921055021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36bc88b06093ed670b3d86f3228a06349f1485d58f309217b1fec3c025cee910 0.600000000000 1631389 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": 1146708, "vin": [ { "gen": { "height": 1146698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36bc88b06093ed670b3d86f3228a06349f1485d58f309217b1fec3c025cee910" } } ], "extra": [ 1, 182, 56, 232, 229, 73, 113, 247, 167, 194, 69, 168, 108, 178, 200, 71, 194, 49, 37, 203, 68, 8, 170, 64, 85, 186, 25, 164, 245, 140, 146, 16, 85, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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