Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 265739b1bb45aeccb50e80e58fad18eda0b2c30f6abc00a5b8fbad7a5e924238

Tx prefix hash: f184a13678aa837f40287bd40bf2ea615e0658dd01b8769a6cf70418665ae47f
Tx public key: 385ac9c8d5493bc369fbfc50e2f05dcad90bcc9dce49ea2e17b8af34b900ef86
Timestamp: 1723104420 Timestamp [UCT]: 2024-08-08 08:07:00 Age [y:d:h:m:s]: 00:251:22:02:36
Block: 1083294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179940 RingCT/type: yes/0
Extra: 01385ac9c8d5493bc369fbfc50e2f05dcad90bcc9dce49ea2e17b8af34b900ef86021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d7ff98d76de36c770754cb6175a971bd654f12bf1871a4ac3d433c7ebf9b04c 0.600000000000 1557155 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": 1083304, "vin": [ { "gen": { "height": 1083294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d7ff98d76de36c770754cb6175a971bd654f12bf1871a4ac3d433c7ebf9b04c" } } ], "extra": [ 1, 56, 90, 201, 200, 213, 73, 59, 195, 105, 251, 252, 80, 226, 240, 93, 202, 217, 11, 204, 157, 206, 73, 234, 46, 23, 184, 175, 52, 185, 0, 239, 134, 2, 17, 0, 0, 0, 4, 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